Skip to content

Conversation

@pi0
Copy link
Collaborator

@pi0 pi0 commented Oct 25, 2025

Moving to #172 due to CI issues

@changeset-bot
Copy link

changeset-bot bot commented Oct 25, 2025

⚠️ No Changeset found

Latest commit: 57ecefc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Contributor

vercel bot commented Oct 25, 2025

@pi0 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

@socket-security
Copy link

socket-security bot commented Oct 25, 2025

@pi0 pi0 changed the title feat: nitro+vite support and workbench feat: nitro+vite support Oct 25, 2025
@pi0 pi0 marked this pull request as ready for review October 25, 2025 07:44
@vercel
Copy link
Contributor

vercel bot commented Oct 25, 2025

You must have Developer access to commit code to Vercel Labs on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes.

Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles

@pi0 pi0 marked this pull request as draft October 26, 2025 07:38
rollupConfig: {
plugins: [workflowRollupPlugin()],
},
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The import of workflowRollupPlugin from 'workflow/rollup-plugin' is unused and should be removed. The rollupConfig that used it was removed on this commit since the Nitro module now handles the plugin injection automatically.

View Details
📝 Patch Details
diff --git a/workbench/nuxt/nuxt.config.ts b/workbench/nuxt/nuxt.config.ts
index ec2c3bc..023f0a9 100644
--- a/workbench/nuxt/nuxt.config.ts
+++ b/workbench/nuxt/nuxt.config.ts
@@ -1,5 +1,4 @@
 import { defineNuxtConfig } from 'nuxt/config';
-import { workflowRollupPlugin } from 'workflow/rollup-plugin';
 
 export default defineNuxtConfig({
   compatibilityDate: 'latest',

Analysis

Unused import of workflowRollupPlugin in nuxt.config.ts

What fails: The import statement import { workflowRollupPlugin } from 'workflow/rollup-plugin'; on line 2 of workbench/nuxt/nuxt.config.ts is dead code - the imported symbol is never used anywhere in the file.

How to reproduce:

  1. Open workbench/nuxt/nuxt.config.ts
  2. Search for any reference to workflowRollupPlugin in the file
  3. The symbol is only in the import statement and never referenced

What happens vs expected: The import exists but serves no purpose. The Nitro module (workflow/nitro) that is loaded via the modules: ['workflow/nitro'] configuration automatically injects the workflow rollup plugin via the Nitro rollup:before hook (see packages/nitro/src/index.ts lines 13-15), so importing it in the config file is redundant and unnecessary.

Expected behavior: The unused import should be removed to keep the configuration clean and avoid confusion.

@pi0 pi0 changed the title feat: nitro+vite support feat: vite + nitro support Oct 31, 2025
@pi0 pi0 closed this Oct 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants